∂02-JUN-75  0913		E,ALS
 Can you come in to talk about the SOS problem? I am in the middle of fixing
 ETV so thaat there will be a /F mode which will allow one to page a /R file
 to any desired page size for convenience in reading it and this is a good time
 for me to fix your problem as well.
␈ CC: rf

∂02-JUN-75  0852		E,ALS
 Most things now work for /F. I am thinking about the following:
 1) Fix it so the default value for a /F value is set to 511 automatically when
 one types /R only. Since the line count is or will be set to zero every time a
 true FF is found, this would do nothing to files that are already paged to smaller
 limits.
 2) Test files that are to be formatted to see if they are paged already to less
 than 511 lines and if not to ask if this should be done. This request could be
 introduced during the directory making process and it would add very little to
 the running time if the pages were all shorter than this limit.
 3) Perhaps reverse the situation and fix it so that pages are always limited in
 size unless the user specifically requests otherwise.
␈ CC: ME

∂01-JUN-75  1813		E,ALS
 When you get the directory pointer invalid message it is wise to stop
 and fix things up. Unless you are in the readonly mode you can do this
 by the CONTROL . command. If it still complains then it is wise to
 leave ETV and reload the offending file. I am at home so I cannot
 look into your trouble very well at the moment but I have gotten a whole
 string of error messages which would indicate that you continued to 
 do what ever it was that led to the message many times, or that ETV was in a loop
 that you did not intercept.
␈ CC: BPM

∂01-JUN-75  1750		E,ALS
 Sorry I was not more specific.
 Mainly I fixwd up the matter of asking about formatting when one had
 typed /F. It seems to me that it should not be necessary to ask
 if it is OK to format when one has typed /F. So now it does not ask
 unless the file seems to be a binary file or if it is from a different
 PPN area than that of the person logged in. I also do not see the reason
 why one still has to store the /F value in FFLINE AND LATER TRANSFER IT TO
 EDFIL-2 so I fixwded it to store both places at once. THE
 remaining bad bug is that `fter one has done a /F/R and then tries to
 go back home with a H command the system still remembers and
 thinks that the home file is /F. I kept a copy of E as you left it as e.41
 so if you want to undo all of this it will be very easy.
␈ CC: me

∂01-JUN-75  1348		E,ALS
 Did you retype the UDP1: over again the second time/∨? If you did not
 this could be the trouble but probably you did and there is a bug. I
 have another related bug which may be due to the same thing. I will
 look into it on Monday.
␈ CC: jam

∂01-JUN-75  1134		E,ALS
 I fixed a few minor bugs but one remains that is very bad. This has to do with
 switching. I thought that if we stored /F in edfil-2 at once on page 63 some of
 these troubles would go away but they did not so I do not understand it correctly.
 This fix is now in however. I will not be able to work much till monday so
 good luck.
␈ CC: ME

∂31-MAY-75  0821		E,ALS
 That is not all that has to be fixed to make E work for the /F/R case. Suppose
 that you enter a file in this way, put some marks on page 1 then go to some other
 page, say 3. E will  copy through to page three ok but no record will be kept as
 to where in the specified records page 2 and page 3 start.
 Now you go back to page 2. Will E have to start all over and read from page 1
 to find the start of page 2? Now you decide to make some additions or deletions
 to page 2, giving the readwrite command  so that these will be accepted and thy to
 go back to your marks on page 3. What will happen? The straight forward way would
 be to redo the directory completely but this will mess up your marks. I hav figured
 how one might make a modification to the directory for the /F/R case to keep an
 additional number in addition to the record number to hold the line offset so that
 E does not have to start all over each time and this should be fairly simple as
 long as you do not make any changes to earlier pages but it would be very messy to
 change everything and create a new directory while taking proper care of marks.
 I am thinking about this but I think that I will ignore the readwrite change
 problem until I get the simple case working.
␈ CC: ME

∂31-MAY-75  0809		E,ALS
 What did you mean telling Taylor that ETV will not now handle SOS files? This
 is news to me. I thought that my fix worked OK. The only thing different should
 be that it tells you that you are trying to format an SOS file and requires
 confirmation that that is what you in fact want to do.	ALS
␈ CC: RF

∂30-MAY-75  1710		E,ALS
 RG is wrong. You can use ETV with SOS files. It does now tell you that
 you are working on an SOS file but if you tell it to cggo Ahread it does
 the right thhngs. It may be that some troubles might occur if you try to
 use ETV over the net. I do not know about thids.  I will get RF to explain
 his objections. 
␈ CC: RHT

∂30-MAY-75  1131		E,ALS
 I fixed the bug in /F and am a fair way along on the /R case. This gets a bit
 hairy if one lets the directory be created incrementally. The trouble is that
 the convenient time to introduce the FF seems to depend upon too many factors.
 I am sure that when I have thought it trrough properly I will find a better way
 than I now see how to do it. The code will definitely have to go somewhere near
 where we first put the /F stuff but certainly not exactly there.
␈ CC: ME

∂29-MAY-75  0946		E,ALS
 We were trying to do too much with too little. I am beginning to see what we
 need to do. We must differentiate between three different cases, that is
 1) /F switch only
 	Format the file with a FF and a new record and new page after every
 	FFLINE number of lines, create and save the new directory.
 2)/F and /N switches both used
 	Same as case 1) above except that the directory is creaated on page 0
 	and is not written out. The file will be rippled and padded out so that
 	the FF's are at the beginning of new records.
 3) /F and /N switches both used
 3) /F and /R switches both used
 	In this case we do not want to ripple the file so a pseudo directory
 is created on page 0 and a record should somehow be kept of the line count
 	at the start of each block so that ETV will not have to read from
 	the beginning every time a new page is switched to.
 One might expect a fourth case when /N, /R and /N are all three given, but
 in this case the /R would take precedence and the /N would simple be ignored.
 
 In case 1) the FFline value would not be written into EDFIL-2, since the value
 would be used only on the first formatting and it would not want to be
 remembered on file switching. This would also apply to case 2).
 in case 3) we would want to save the FFLINE value so that when the file is
 recalled by number we would recall the value and the same pseudo directory
 would be recreated.
␈ CC: ME
This is a file to save outgoing mail.